Architectural Implications of Common Operator Interfaces

If a common operator interface (COI) for satellite ground systems is built with conventional user interface (UI) technology, then there is substantial risk that the UI will end up determining a significant part of the ground system’s architecture. UI technology typically forces applications to be constructed as a set of call-backs to the UI. To avoid this situation an approach is required which sharply divides the user interface part of the system from the rest of the software. If the ground system is to run on heterogeneous hardware platforms a second sharp separation is also recommended: presentation and dialog decisions from platform specific toolkits. This presentation suggests a multi-level solution to this problem which is established at the architecture level and maintained in the implementation.